These commands are used to configure plugins. They should appear, one per line, at the top of files to be used as plugins.
*COMMAND commandName minAccess
Makes a new command responding to commandName. For this command to execute, the person executing it must have access of at least minAccess.
The entry point for this type of plugin is the first command of the script, or at the line after an @ENTRY commandName, if one is found. Command names are limited to 30 characters.
*ALIAS command mappedTo
Aliases a command to another. For example, "*ALIAS Q DIE" would map !Q to !DIE.
*LIST command minaccess
The file is treated as a list. The URL plugin is a good example. See the Lists file for more information.
*ONTEXT "textMask" minAccess maxAccess
This can be used to make the bot respond to text typed in the channel. If the user's access level falls between minAccess and maxAccess, or is greater than minAccess if maxAccess = 0, and the text matches the textMask, the script is executed.
Example: *ONTEXT "*zzz*" -1 900
if someone types 'zzz' anywhere in a string, and their access is under 901, the script is executed.
If you are mixing ONTEXT and COMMAND entries in a single file, the entry point for an ONTEXT is either the top of the script, or an @ENTRY of the textMask (sans quotes), for example, @ENTRY *zzz*
*WRITELN theText
Outputs theText to the console when the script is loaded at program launch.
*GLOBAL type name [initial value]
Creates a variable for the last defined plugin. Valid types are 'str' (string), 'int' (integer), and 'bool' (boolean) (no quotes). If the initial value is set, the variable is set to that value. For booleans, "TRUE" (no quotes) sets it to true; all other values set it to false.
*MAXRUNNING <number>
If this configuration command is found, and number > 0, the last *COMMAND or *ONTEXT is limited to number simultaneous executions.
*ENDCONF
Anything after this is not processed. It's a very good idea to put *ENDCONF in, especially if your plugin is long, because it speeds up launch time.
Configuration commands should be located at the top of your plugin file, or in a file with the same name as the plugin with a '.h' after it.